What would the right way to implement #4562 with the new API be?

Here's a quick dump of what I'm thinking of doing now:

• Bring in all cache-management code into one place
• Introduce a new sdist cache; with egg-info {and in future dist-info}
• Move out the common parts of the 2 caches into a common (abstract?) base class

Once this is done, it'll be possible for @alex to use the base class (either by subclassing or by directly using it, depending on whether it's abstract) for the temporary cache. This is why I wrote #4562 (comment).

_{edit: use name; not "you"}

Here's a quick dump of what I'm thinking of doing now

Oh, and yes... anyone's inputs on this are more than welcome. ^.^

What would the right way to implement #4562 with the new API be?

@alex I just gave this a bit more thought - I think you can just use WheelCache directly using a temporary directory as it's cache_dir? Then these changes would leave you un-affected plus it would also be more clear in that it is using the abstraction it's supposed to... :)

Pinging @dstufft for a review. :)

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.